[Pkg-systemd-maintainers] Bug#725422: Bug#725422: Bug#725422: Bug#725422: systemd set kernel.sysrq=16
kreijack at inwind.it
Sat Nov 30 07:13:41 GMT 2013
On 2013-11-29 20:53, Zbigniew Jędrzejewski-Szmek wrote:
> Hi Goffredo,
> On Thu, Nov 28, 2013 at 10:19:41PM +0100, Goffredo Baroncelli wrote:
>> Hi Michael,
>> On 2013-11-28 21:51, Michael Stapelberg wrote:
>>> Hi Goffredo,
>>> Goffredo Baroncelli <kreijack at inwind.it> writes:
>>>> Systemd has as main target Fedora. Debian is different from Fedora, so
>>> systemd is not targeting one distribution as its main target. It is
>>> running on many distributions, with no particular focus on any single
>>> one of them.
>> Let me rephrase this sentence: systemd is not sensible to the debian
>> requirements; otherwise there would not be the problems to support the
>> other debian kernels (like hurd and bsd).
> Even if this were true, this bug report is not about hurd or bsd.
> Since this is a bug report, let me ask again: is there anything to fix
> with the sysctl stuff?
As reported in my first report :
> Problem description:
> After installing the systemd package some sysrq keys don't work any more.
> Expected behaviour:
> The systemd package must not interact with the sysrq key setting
I am trying to send a patch to systemd-devel to split the content of the
systemd sysctl config file in smaller file to simplify the overriding of
the single file.
Worse, the workaround which I found  will be nullified with the new
systemd versions because it is changing the processing order of the
sysctl files configuration..
IMHO The big problem is that there is a sysctl setting as "side effect"
of systemd. It would be a "debian" setting.
Thanks in advance for your work (packaging, testing, talking with the
bug highlighter :-) ).
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
More information about the Pkg-systemd-maintainers