| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
for autosetup -a macro
|
| | |
|
| |
|
|
| |
in Mageia specfile
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Instead of placing the custom files with the upstream files it seems
clearer to have them mostly separated. This makes it easier to see which
parts are custom and which parts are more or less upstream.
As a result the upstream Makefile only needed minor changes to
accomodate this. The Makefile is NOT bug free, unfortunately it doesn't
always do the right thing, this due to inexperience.
|
| |\
| |
| |
| | |
10.04 release
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Resolve problem when wasn't installed chkconfig package. BZ #1716386
|
| | |
| |
| |
| |
| | |
GitHub displays the tag message when we create new release there,
so lets have message with more sense...
|
| | |
| |
| |
| |
| |
| |
| |
| | |
GitHub will create a new commit with different hash (merge) when
applying the pull-request, and so the tag ended up pointing to wrong
commit hash...
For now we have to tag the release commits manually.
|
| | |
| |
| |
| |
| |
| | |
This will allow services to install drop-in files into these folders
for the 'readonly-root' service, but that service won't have to be
installed by default as a result...
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Resolves: RHBZ#1585321
|
| | |
| |
| |
| | |
This concept is quite outdated, and not sane to use at all.
|
| | |
| |
| |
| | |
Use 'git log' instead...
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This installs the real scripts into /etc/sysconfig/network-scripts
while leaving the management of the launchers in /usr/sbin to the
alternatives system.
This allows coexistence with alternative implementations of ifup
and ifdown, notably NetworkManager.
A priority of 90 is chosen rather arbitrarily, NetworkManager will
use a lower one (50) so that our implementation takes precedence over
NetworkManaager in case both are installed. In an unlikely event the
user will want to switch to NetworkManager implementations when both
are installed they can override the default with:
$ update-alternatives --config ifup
|
| | |
| |
| |
| |
| | |
'check' and 'syntax-check' rules were dropped, as they seem obsolete
nowadays (we are not using them at all)...
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
These are no longer appropriate and display managers should be started
by the appropriate systemd unit.
We should have code that enables the appropriate unit automatically
on install now that /etc/sysconfig/desktop has been deprecated.
|
| |\ \
| |/
| |
| | |
Tag as 9.78
|
| | |
| |
| |
| |
| | |
The symlinks are no longer needed. Enablement of default services is
now managed by 'fedora-release' package.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using this package was very dangerous, and could lead to instability
of system, or even being unable to bootup at all, and value of this
functionality was at least questionable, and was not documented.
We decided to drop functionality completely, to make sure users do not
install it accidentally (e.g. by using globbing with 'dnf install').
Resolves: #69
|
| | |
| |
| |
| |
| | |
Users can still create the /etc/sysconfig/init file manually to
override the default values, which are now taken from init.d/functions.
|
| | |
| |
| |
| | |
This is a follow up to 13d638c0a7df4a998429163b9a0189dcffa2393a.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we are creating rpm, we install initscripts to chroot,
so the ROOT variable is set. And since we need that directory
in the package [1], we would have to create it in spec file
anyway.
[1] https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
This reverts commit b119d37d1929a09e25bf288d0273aaaf8c7de86e.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| | |
Move everything to github
|
| | |
| |
| |
| | |
autorelabel was moved to selinux package
|
| |\ \
| |/
| |
| | |
Tag as initscripts-9.58-1
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was disabled upstream, but we inherited a Mandriva systemd-ified
version of this. Let's kill it off.
Originally fixed upstream in ba3f278b5d916b646e8cfca25cd32e3b8acf523e:
Don't frob the console loglevel on boot. (#621257, #626572)
1) This didn't do anything useful prior to rsyslog, as sysklogd would reset it.
2) This overrides the kernel commandline, for people who want to temporarily reset it there
3) This actually turns messages back on out from underneath plymouth, which isn't nice.
To frob the console loglevel, pass it on the kernel command line.
|
| |\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Tag as initscripts-9.55-1
Conflicts:
Makefile
lang.csh
lang.sh
po/Makefile
ppp/ip-down
ppp/ip-up
rc.d/init.d/network
service
sysconfig.txt
sysconfig/init
sysconfig/network-scripts/ifdown-ppp
sysconfig/network-scripts/ifup
sysconfig/network-scripts/ifup-eth
sysconfig/network-scripts/ifup-ippp
sysconfig/network-scripts/ifup-ppp
sysconfig/network-scripts/ifup-wireless
sysconfig/network-scripts/network-functions
sysctl.conf
systemd/fedora-storage-init
Notes:
ppp support was dropped upstream so we will need to merge
it into the ppp package as Fedora has done.
The fedora-storage-init stuff has been dropped. LVM+Raid
is typically initialised automatically now via udev rules
etc. We should try and follow suit, but may need to add
the legacy script back in for now.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
required versions that allow us to do so. (<prajnoha@redhat.com>)
|
