From owner-svn-src-head@freebsd.org Thu May 18 21:29:13 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34B67D6F603; Thu, 18 May 2017 21:29:13 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E901CDA8; Thu, 18 May 2017 21:29:12 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 1A8A03215; Thu, 18 May 2017 21:29:12 +0000 (UTC) Date: Thu, 18 May 2017 23:29:11 +0200 From: Baptiste Daroussin To: Ian Lepore Cc: John Baldwin , rgrimes@freebsd.org, Ngie Cooper , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r318441 - in head/etc: . cron.d Message-ID: <20170518212911.mstgmzbydsv7oind@ivaldir.net> References: <201705180625.v4I6Pd9j062495@repo.freebsd.org> <201705180956.v4I9uVpQ065465@pdx.rh.CN85.dnsmgr.net> <20170518130932.eo5clhki4za2vigz@ivaldir.net> <2201156.H7EQSgYph9@ralph.baldwin.cx> <20170518212429.rugl6vnv5d2b2hpb@ivaldir.net> <1495142869.89384.18.camel@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3mk2o7g3rtz22ydu" Content-Disposition: inline In-Reply-To: <1495142869.89384.18.camel@freebsd.org> User-Agent: NeoMutt/20170428 (1.8.2) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2017 21:29:13 -0000 --3mk2o7g3rtz22ydu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 18, 2017 at 03:27:49PM -0600, Ian Lepore wrote: > On Thu, 2017-05-18 at 23:24 +0200, Baptiste Daroussin wrote: > > On Thu, May 18, 2017 at 09:48:25AM -0700, John Baldwin wrote: > > >=20 > > > On Thursday, May 18, 2017 03:09:32 PM Baptiste Daroussin wrote: > > > >=20 > > > > On Thu, May 18, 2017 at 02:56:31AM -0700, Rodney W. Grimes wrote: > > > > >=20 > > > > > >=20 > > > > > >=20 > > > > [...] > > > The support for broken out files has long been there, but the base > > > system has > > > not used them previously for default config shipped during a > > > release.=A0=A0That > > > is in fact a new trend. > > >=20 > > > However, the current approach seems to be the absolute worst way to > > > do this. > > > If someone wants to use the existing base system image and modify > > > it with > > > config management, they now have to use a mix of styles (for some > > > services > > > edit a global config file for certain settings, but use a dedicated > > > file for > > > other settings for the same service, or for the same settings but a > > > different > > > service).=A0=A0It's also the worst case for humans trying to work with > > > our system > > > as the division between which services are broken out vs global is > > > inconsistent and arbitrary. > > >=20 > > > Once you split up the files you make a merge conflict for anyone > > > trying to do > > > an upgrade.=A0=A0If we do this piecemail then we create N merge > > > conflicts for users > > > to deal with as opposed to if you split it up all at once. > > >=20 > > > Also, there wasn't a clear consensus (a mail to arch@ with "hey, we > > > should > > > switch to splitting up config files for reasons A and B and let's > > > do this for > > > 12.0 but not merge to stable so there is a clear flag day / sign > > > post for users > > > to manage upgrades".=A0=A0Instead there have been a couple of commits > > > and any > > > not-in-100%-agreement opinions are ignored. > > >=20 > > That's true, another thing is the way it is done, there is no simple > > way to > > disable the at cron from an admin point of view=A0=A0rather than rm > > /etc/cron.d/at > > for an end user which an upgrade will bring back. > >=20 > > Bapt >=20 > Would you not just comment out or delete the line, exactly as you would > do in the main /etc/crontab? Right but with a .d directory I would expect to just remove/add files/symli= nks rather than editing it, which defeat the point of the .d Bapt --3mk2o7g3rtz22ydu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlkeEicACgkQY4mL3PG3 Plqw3hAA3I6Ii8MRR4r9vPjAdy5TbyA75eDgyMnyBAlVpyFuFXY8isxVo8q+n8HE FyggrevSV92QM9bJxFp4aqDDr/IMuyNkRbq4WoVLOwQqOweEggI26Fj2gno0wrwa 1OsCKzcVS2bLJ+dvWoLXb9WJevoBE+jdblUToFSebi/P9zGDshMkoaAZpwN7nK1K K2swi5zJsb1Xjmz2hnpMcktDuXr9C3bsHRhsq54g6LZPmiS/Nfl698FZQR2e+fPP l74R0OLpGyiVfJ7AGzFM9Fngv7R9M85LU/9dCcBzvhmiHHXAIxSGn9q0JaxIq2TL q/GKIiKwGazB8aU9mbbfcsuPxOlJcFPJEFl6UZ/kWG+11TO8N71QfJMnn6R5um+a ACjEzA0z2E/Ut81fX+B5d56GCfbKEyYj/ODaMst4tfMwWzTrw1Vc0GrTyM38EdLG vC/nTTr2fbULqs5FwdK32hMSQfzdPonQst4D8gtZ9YLvBQ2ALtc3iVG025o6iaJN ajgUgD0/ncRAC5KP/9gDdbaRfTvoEVQWO4i3JVHotckDvfXjTgJjmgzI1eHSu1v7 iTdokuDlIX0wup0fGjUw2i9/cusF0ehUHijhORLdkFAiIvXunPcZ5ihZhHtLtGxq 9ss6eN5npl/zWIjLTtCFMOG7wixgctv0FePnfVk3QiBN060dgw4= =bc2S -----END PGP SIGNATURE----- --3mk2o7g3rtz22ydu--