Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: runit-kdump: fix conflict with /usr/lib/sysctl.d/10-void.conf
Date: Tue, 04 Aug 2020 15:31:40 +0200	[thread overview]
Message-ID: <20200804133140.CNWiQUtUR_jHksgh34zjgInOSbi9wWqbtFGDdMMh3CQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21491@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

There's a merged pull request on the void-packages repository

runit-kdump: fix conflict with /usr/lib/sysctl.d/10-void.conf
https://github.com/void-linux/void-packages/pull/21491

Description:
`/etc/runit/core-services/08-sysctl.sh` is run before `/etc/runit/core-services/90-kdump.sh`
This results in loading `/usr/lib/sysctl.d/10-void.conf` before running kdump kexec.
There is a problematic section in that file:
```
# Turn off kexec, even if it's built in.
kernel.kexec_load_disabled=1
```
This results in kdump failing to load. This option can't be turned off once it's turned on, as per [sysctl documentation](https://www.kernel.org/doc/html/latest/admin-guide/sysctl/kernel.html#kexec-load-disabled).
If this option is to be enabled kdump has to be loaded before the option is enabled.
This pull request renames `90-kdump.sh` to `07-kdump.sh` so it's loaded before `08-sysctl.sh`
I have tested this on my machine and it works on it.

There are probably other solutions as well, so please comment if you have any ideas.

      reply	other threads:[~2020-08-04 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 15:03 [PR PATCH] " klarasm
2020-08-04 13:31 ` leahneukirchen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200804133140.CNWiQUtUR_jHksgh34zjgInOSbi9wWqbtFGDdMMh3CQ@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).