| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
10.04 release
|
|
|
|
| |
since ~2011
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
It was added in commit be75c98a06d569fbaa2d86f92676af961795d094 as part
of a big 'Mageia patch' commit. At least since the commit (2011) this
script was never installed or packaged. Further, the bootloader-utils
spec file has scripts to remove this file!
|
| |
|
| |
|
|
|
|
|
|
|
| |
This script was used to make it easier to merge our initscripts fork
with upstream. script is heavily outdated and as a result, unusable. It
e.g. assumes upstream uses SVN and we're using SVN. The instructions
within README.md are way more useful.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rebuild of the dkms modules should not be triggered by mandrake_everytime
which is itself triggered via mandriva-everytime.service, as people might
want to disable this service, as harddrake often takes a lot of time to run
and hence blocks the boot.
This has been split out into a separate script into the dkms package,
/usr/sbin/dkms-autorebuild.sh including a systemd service that calls this on
every boot and some documentation was added to the script on how to disable
the dkms module rebuild.
Overall the same should be done for all the other parts of mandrake_everytime
to split them out into separate scripts to msec, harddrake and other affected
packages after reviewing them to be able to kill mandrake_everytime legacy.
mga#17194
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note: I think this is bogus. It doesn't deal properly with homedirs
on NFS with SECURE_TMP set as many programs require filesystem
behaviour that NFS cannot honour. If anything, the tmp folder
should be mounted as tmpfs.
Ultimately however this is what XDG_RUNTIME_DIR is meant to
do and programs should generally move away from it.
I'd suggest even that TMP and TMPDIR point to /run/user/603/tmp
if you want a really secure TMPDIR system.
Or at least something along those lines.
mga#14778
|
|
|
|
|
|
| |
This has been dead for some time I believe. All desktops these days utilise
udisks for automounting and such like with proper ACL and access control
to the active user of the seat that the device/port belongs to.
|
|
|
|
| |
This has been obsolete for a while, so this is just housekeeping.
|
|
|
|
|
| |
This is no longer called as it is masked by a prefdm systemd
unit but even that will die soon enough.
|
|
|
|
|
| |
The previous merge pulled in this for all the upstream stuff, so
we should follow suit
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
systemd sometime after 195 changed the behaviour of LSB sysvinit compatibility.
Previously a require name of 'network' would be mapped to network.service, but
now it will map to 'network.target' due to 'network' being a common name
used in initscripts with a special meaning.
The initscript has a 'Provides: $network' header which maps to a systemd
unit directive of 'Before=network.target', with the Required-Start header
it also got a 'After=network.target' which obviously creates an ordering
loop.
In actual fact we pull in the network.target which in turn pulls in
network.service anyway, so there is little harm in dropping this.
|
|
|
|
| |
Originally by Colin Guthrie, but rewritten by me.
|
|
|
|
|
|
| |
drakx-net is listening for events coming from mageia.org
This should fix detection of connection success/failure in net_applet,
draknetcenter and drakroam.
|
|
|
|
|
|
|
|
|
| |
Also no need to shell out to logger as this is typically started by
systemd and thus any stderr output will end up in the journal (and
by extension syslog if it's installed).
Might help avoid numerous reports of the service 'failing' as
indicated in mga#8472.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
LESS=-MM breaks colorized output of git, and maybe perl-doc as well
(Mdv #57143).
It seems no other distro is shipping this as default,
should be safe to remove.
|
| |
|
|
|
|
|
|
| |
This can happen on the ifcfg-Auto* files created by NM. It may be
more sensible overall to just skip such files, but incase any other
invalid files are found, they are now simply skipped to avoid errors.
|
|
|
|
|
|
|
|
|
|
|
| |
As harddrake is run by mandrake_everytime (which starts Before=basic.target)
and it, in turn may try to start cpufreq (which starts After=basic.target)
a deadlock can occur.
To work around this, we pass the --no-block option to systemctl
to return flow and allow us to continue.
Hopefully solves mga#4772
|
|
|
|
|
|
|
| |
Trust link detection to Network Manager rather than doing more work ourselves.
Also ensure we wait for resolvconf even when we are using NM as this is still
needed.
|
|
|
|
|
|
|
|
| |
This change ensures that systemd will wait until this script
completes (and thus network is up) before we allow any logins.
Also provide $named such that this translates to nss-lookup.target in
systemd.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Both scripts will check to see if NetworkManager is running before deciding
to ignore interfaces. This directive will ensure that systemd starts
NetworkManager before running these scripts and thus any checks and probes
will be valid.
This should prevent the double running of wpa_supplicant if the network
script was run before NetworkManager which can cause constant disconnects.
|
|
|
|
| |
Also do not wait for NM devices with no link.
|
|
|
|
| |
Like done upstream in commit 300aaee62cd7a3166969e795b53b065c510e09c1
|
| |
|
|
|
|
| |
https://bugs.mageia.org/show_bug.cgi?id=1216
|
|
|
|
|
|
|
| |
When building gcc/ecj1, TMP/TMPDIR is used and this results in debugedit
being unhappy.
(patch originally from svn: 77112 rtp - Remove trailing whitespace at the end of TMPDIR/TMP)
|
| |
|
| |
|
|
|