initscripts, branch 9.74

9.74-1

2017-08-04T14:43:56+00:00

Makefile: fix whitespace error in commit b119d37d1

2017-08-04T14:17:31+00:00

9.73-1

2017-08-03T14:09:54+00:00

Makefile: replace /var/run with /run

2017-08-03T11:47:59+00:00

Do not create anything under /run when $(ROOT) is non-empty: when
we're installing into a chroot /run might not be mounted, and
creating files there is counterproductive.

Replace /var/run with /run everywhere

2017-08-03T11:47:59+00:00

https://bugzilla.redhat.com/show_bug.cgi?id=1471489

Update references to sysctl.conf

2017-07-27T13:45:50+00:00

This file hasn't been called that for a while, so update various
references to the new sysctl.d names.

Drop sysctl.d/00-system.conf

2017-07-27T13:45:50+00:00

This file now only contains lines to disable netfilter on bridges.
In kernel 3.18 this filtering functionality was made non-default by
moving it to br_netfilter [https://bugzilla.redhat.com/show_bug.cgi?id=512206].
Aybody who actually wants to use br_netfilter has to load it explicitly
anyway, so disabling it through sysctl isn't necessary anymore.

The reason for removal is that by default (i.e. when br_netfilter is
not loaded), we get a warning on every boot:

systemd-sysctl[210]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
systemd-sysctl[210]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
systemd-sysctl[210]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory

This is confusing for users and inelegant.

The downside of removing this file is for people who load br_netfilter
for some reason *and* do no want to use it, will have to take an
additional step now (either restore the sysctl settings or remove br_netfilter
from /etc/modules-load.d or wherever). I expect the number of people affected
to be very small.

(Note that the file was overwritten on sparc and s390, so those
architectures see no change.)

Drop 256term.{sh,csh}

2017-07-21T13:16:35+00:00

From https://fedoraproject.org/wiki/Changes/Drop_256term.sh:

  This is a work-around and it's better to for the terminal emulator
  to set $TERM properly on its own. Various terminal emulators have
  been updated to do that.

When those scripts are removed, whatever the virtual terminal or
terminal emulator sets as $TERM will be used.

Fixes #107.
C.f. https://bugzilla.redhat.com/show_bug.cgi?id=1165439.

ARPUPDATE introduced

2017-07-14T15:22:22+00:00

  The ARPUPDATE option has been introduced. It defaults to 'yes'.

  By setting the ARPUPDATE to 'no', administrator can disable
  updating neighbouring computers with ARP information about current
  NIC. This is especially needed when using LVS Load Balancing with
  Direct routing enabled.

9.72-1

2017-05-25T15:58:04+00:00