| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
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)...
|
| |
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
required versions that allow us to do so. (<prajnoha@redhat.com>)
|
| |
|
|
| |
where the defaults now live. (#760254)
|
| | |
|
| | |
|
| |
|
|
| |
The profile support itself was removed a while ago.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for legacy initscript actions such as
service iptables save
Packages wishing to provide legacy actions should install programs (probably
scripts, but could be binaries) named
/usr/libexec/initscripts/legacy-actions/<service>/<action>
It should be emphasized that this feature is meant to be used only in packages
where compatibility of custom actions with previous releases is desired.
Adding of entirely new actions is discouraged. Useful tools should be
shipped by upstreams as programs in /usr/bin, not in distro-specific hacks.
[ Modifications from original : change from /usr/lib to /usr/libexec - notting ]
https://bugzilla.redhat.com/show_bug.cgi?id=796663
|
| |
|
|
|
|
| |
(#760254)
Also, update apply_sysctl to 1) use systemd-sysctl if it's there 2) imitate it if it's not.
|
| |
|
|
|
|
|
|
| |
This service imports the contents of /run/initramfs/state into the root
filesystem, where the root filesystem is writeable.
This allows dracut to hand the ifcfg file and dhclient lease over to
NetworkManager on network-booted Live images.
|
| | |
|
| | |
|
| |
|
|
| |
udev/systemd combination anyway.
|
| |
|
|
| |
/var/lock on tmpfs.
|
| |
|
|
| |
non-late version. (#699918)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Writing /.autorelabel from fedora-autorelabel does not work because the
script is executed only if relabel was already requested.
Create a new unit fedora-autorelabel-mark.service which will be
responsible for creating /.autorelabel if SELinux is disabled.
The unit takes advantage of the new "ConditionSecurity=" support in
systemd.
The old script checked for a read-only filesystem first. The new unit
does not do that. If / is read-only, touch will simply fail. This should
not be considered as a failure of the unit, so "-" is used in ExecStart.
There have been arguments on systemd-devel that the root directory
should not be abused for flag files like /.autorelabel. It has a long
tradition in Fedora though (since 2005). Maybe we can change it
eventually, but let's keep it where it is for now.
|
