[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-dev
Subject: Re: [gentoo-dev] Policy regarding enablement of drop-in configuration files
From: Alec Warner <antarus () gentoo ! org>
Date: 2015-03-31 21:21:10
Message-ID: CAAr7Pr_9qkn7yX=UwXUnACPu9F8Pupayifx4XcTDWqFHBhsqxA () mail ! gmail ! com
[Download RAW message or body]
On Tue, Mar 31, 2015 at 11:14 AM, Mike Gilbert <floppym@gentoo.org> wrote:
> Hi all,
>
> I have been bumping heads with Mike Frysinger (vapier) on the topic of
> drop-in config files that are utilized by quite a few system services
> on Gentoo. For reference, see bug 544150.
>
I am going to the movies with Mike tomorrow, I will be sure to cuddle him
on your behalf.
>
> Mike claims that Gentoo has a policy of "not enabling anything by
> default", and that this policy applies to both init scripts, and
> drop-in configuration files.
>
I would say the policy for *services* is that non-critical services are not
enabled by default. I would argue that is a policy decision that is distro
wide.
Maintainers are of course, at liberty to determine if their service is
'critical' or not.
>
> I counter that we have no such policy. We don't generally enable init
> scripts by default because that just makes logical sense. Mike F. is
> trying to apply this same logic to drop-in configs, and that just
> doesn't fit.
> Regarding drop-in configuration files, there are many examples where
> these are generally enabled by default, or it is left to the
> maintainers discretion:
>
> - udev rules are enabled by default
> - crontab entries are left to the maintainer, but are generally
> enabled by default
> - tmpfiles.d entries are enabled by default
> - logrotate entries are enabled by default
> - binfmt.d entries are enabled by default
>
> Further, the way many of these services is designed does not allow for
> the drop-in configs to be easily disabled by default by the OS vendor.
> However, in most cases, they may be disabled by the sysadmin by use of
> an overriding drop-in config somewhere under /etc.
>
> My questions to the community:
>
> - Do we have a policy regarding enablement of drop-in config files?
>
Maintainers discretion.
> - If so, what is it? Where is it documented?
>
My brain; seriously though, generally undocumented things imply maintainers
discretion.
> - If not, do we need a policy and what should it be?
>
I hope not; but if you do something silly, be prepared to get called on it.
> - Keep in mind that any policy needs to be technically feasible to
> implement.
[Attachment #3 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar \
31, 2015 at 11:14 AM, Mike Gilbert <span dir="ltr"><<a \
href="mailto:floppym@gentoo.org" target="_blank">floppym@gentoo.org</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">Hi all,<br> <br>
I have been bumping heads with Mike Frysinger (vapier) on the topic of<br>
drop-in config files that are utilized by quite a few system services<br>
on Gentoo. For reference, see bug 544150.<br></blockquote><div><br></div><div>I am \
going to the movies with Mike tomorrow, I will be sure to cuddle him on your \
behalf.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Mike claims that Gentoo has a policy of "not enabling anything by<br>
default", and that this policy applies to both init scripts, and<br>
drop-in configuration files.<br></blockquote><div><br></div><div>I would say the \
policy for *services* is that non-critical services are not enabled by default. I \
would argue that is a policy decision that is distro wide.</div><div>Maintainers are \
of course, at liberty to determine if their service is 'critical' or \
not.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
I counter that we have no such policy. We don't generally enable init<br>
scripts by default because that just makes logical sense. Mike F. is<br>
trying to apply this same logic to drop-in configs, and that just<br>
doesn't fit.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> Regarding drop-in configuration files, there are many \
examples where<br> these are generally enabled by default, or it is left to the<br>
maintainers discretion:<br>
<br>
- udev rules are enabled by default<br>
- crontab entries are left to the maintainer, but are generally<br>
enabled by default<br>
- tmpfiles.d entries are enabled by default<br>
- logrotate entries are enabled by default<br>
- binfmt.d entries are enabled by default<br>
<br>
Further, the way many of these services is designed does not allow for<br>
the drop-in configs to be easily disabled by default by the OS vendor.<br>
However, in most cases, they may be disabled by the sysadmin by use of<br>
an overriding drop-in config somewhere under /etc.<br>
<br>
My questions to the community:<br>
<br>
- Do we have a policy regarding enablement of drop-in config \
files?<br></blockquote><div><br></div><div>Maintainers discretion.</div><div> \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
- If so, what is it? Where is it documented?<br></blockquote><div><br></div><div>My \
brain; seriously though, generally undocumented things imply maintainers \
discretion.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
- If not, do we need a policy and what should it \
be?<br></blockquote><div><br></div><div>I hope not; but if you do something silly, be \
prepared to get called on it.</div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
- Keep in mind that any policy needs to be technically feasible to \
implement.</blockquote></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic