Control: reopen -1 On Mon, 2014-02-17 at 13:19 +0100, Michael Biebl wrote: > Ben, you just closed the bug again. I assume this was by accident?
Bother. Yes. > Am 17.02.2014 11:45, schrieb Debian Bug Tracking System: > > On Wed, 2013-11-27 at 20:19 +0100, Michael Stapelberg wrote: > >> > Hi Goffredo, > >> > > >> > Goffredo Baroncelli <[email protected]> writes: > >>>> > >> Solved, the configuration file should be processed *before* the > >>>> > >> default > >>>> > >> file. > >>>> > >> So I named the file /etc/sysctl.d/01-sysrq.conf. > >>> > > > >>> > > Unfortunately the things are even more complex. Recently systemd > >>> > > changed > >>> > > behaviour: with the latest version (207) the configuration must be > >>> > > processed after the systemd default file: so the file will must be > >>> > > named > >>> > > /etc/sysctl.d/99-sysrq.conf. > >> > Thanks for the heads-up. > >> > > >> > >From the discussion I take it that there is no actual bug here, so I’m > >> > closing this report. > > There is a bug. You should not ship /usr/lib/sysctl.d/50-default.conf . > > > > The default sysrq mask was reviewed some years ago by the kernel > > maintainers and a sensible default (not 1) is set in official kernel > > packages. This should not be overridden just because people switch to > > systemd; nor should anyone else's customisation in /etc/sysctl.conf or > > kernel build config. > > The downside of this approach obviously is, that as soon as you switch > kernels (e.g. use a self-compiled one), this setting changes. That is the choice of the person configuring the kernel, and should be respected. If they start with the Debian configuration and linux-source-<version> package then they will get the same initial value for kernel.sysrq. Starting with 3.13, that also works with upstream source as the addition of a config symbol for the initial value was accepted upstream. > So explicitly setting the sysrq key imho has benefits. > > Do you remember, why you decided against using a sysctl.d snippet? Why would a kernel package do that? It already contains the defaults and has no need to override them. > Let me also add, that custom modifications, if done via /etc/sysctl.conf > should be preserved, i.e. once [1] is fixed > > Do you also happen to remember where this discussion happened so we have > some reference for this bug report. > > Michael > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737184 https://bugs.debian.org/564079 Ben. -- Ben Hutchings You can't have everything. Where would you put it?
signature.asc
Description: This is a digitally signed message part
