HI Michael, On 2013-11-27 22:57, Michael Stapelberg wrote: > Hi Goffredo, > > Goffredo Baroncelli <kreij...@inwind.it> writes: >> As already written I am not complaining about the specific systemd >> sysctl values, nor the fact that systemd sets some values during the >> boot. I am complaining that if an user install systemd, he got some >> sysctl values changed. > Can you send a patch to upstream which will make systemd use a different > way of achieving that default? If you’ll get it accepted, I’ll gladly > cherry-pick it and include it in the next Debian upload. > > Otherwise, I don’t feel comfortable modifying the upstream software > package for such a minor detail.
Thanks for your reply and for your time. However I cannot agree with your conclusion: having some setting changed only because I installed an unrelated package it seems me a bad behaviour and definitely not a "minor detail". So please don't close this bug. I agree with you, that it is a problem of systemd and of its tendency to force its "standard" everywhere. But it is its right to do so [1]. What I am expected by debian package is to filter these issues. I will highlight this also to upstream. But it would help me if you don't close this bug. BR G.Baroncelli [1] I repeat I am not arguing about the values, I am arguing that a package which aim to replace the init must change a setting which aren't related to the package functionality. -- gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
