Is there a reason we do not turn on the file system hardlink/symlink protection in Rawhide?

[Josh Boyer]

On Thu, Mar 14, 2013 at 8:28 PM, Chris Adams <cmadams at hiwaay.net> wrote:
> Once upon a time, Lennart Poettering <mzerqung at 0pointer.de> said:
>> Hmm, I'd very much prefer if the defaults are built into the kernel, and
>> that sysctl in userspace is then used only by the admin to override these
>> defaults, so that by default we ship with empty sysctl.d/ dirs.
>>
>> So, before I merge anything like this into systemd, why can't the kernel
>> default setting simply be flipped?
>
> Upstream kernel said "no, distros can do it in userspace", and Fedora
> aims to remain true to upstream.  Also, if upstream kernel does one
> thing and Fedora kernel the opposite, users would have unexpected
> defaults changing if they built their own kernel for some reason.
>
> Why would this need to be merged into systemd?  Why not just sysctl.conf
> (or I guess the new-and-improved /usr/lib/sysctl.d/00-system.conf, which
> comes from initscripts)?

My patch put it in /usr/lib/sysctl.d, just coming from systemd itself.
We could possibly throw that file into initscripts if systemd doesn't
want to make that change (though I think Lennart would have the same
objection).

josh