Date: Thu, 18 May 2017 23:36:23 +0200 From: Baptiste Daroussin <bapt@freebsd.org> To: Ian Lepore <ian@freebsd.org> Cc: John Baldwin <jhb@freebsd.org>, rgrimes@freebsd.org, Ngie Cooper <ngie@freebsd.org>, 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: <20170518213622.r66gzsjlvj76ujli@ivaldir.net> In-Reply-To: <1495143278.89384.24.camel@freebsd.org> 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> <20170518212911.mstgmzbydsv7oind@ivaldir.net> <1495143278.89384.24.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--3iqfx6deqp4ggs2f Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 18, 2017 at 03:34:38PM -0600, Ian Lepore wrote: > On Thu, 2017-05-18 at 23:29 +0200, Baptiste Daroussin wrote: > > On Thu, May 18, 2017 at 03:27:49PM -0600, Ian Lepore wrote: > > >=20 > > > On Thu, 2017-05-18 at 23:24 +0200, Baptiste Daroussin wrote: > > > >=20 > > > > On Thu, May 18, 2017 at 09:48:25AM -0700, John Baldwin wrote: > > > > >=20 > > > > >=20 > > > > > On Thursday, May 18, 2017 03:09:32 PM Baptiste Daroussin wrote: > > > > > >=20 > > > > > >=20 > > > > > > On Thu, May 18, 2017 at 02:56:31AM -0700, Rodney W. Grimes > > > > > > wrote: > > > > > > >=20 > > > > > > >=20 > > > > > > > >=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 > > > 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/symlinks > > rather than editing it, which defeat the point of the .d > >=20 > > Bapt >=20 > Hrm, I don't see any conflict between "this fine-grained file holds > config for just one component" and "edit the file if you want to change > the config". =A0That is, making the file fine-grained is to make editing > it EASIER (for a human or a program), not to eliminate editing it. >=20 > I do see how thinking that deleting the file (or renaming it to file.no > or something) would seem like the right thing to do. =A0How can we fix > that? >=20 For now I don't know :) I'm thinking about it Bapt --3iqfx6deqp4ggs2f Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlkeE9YACgkQY4mL3PG3 PlolkQ//VfPKh64vfEONbmuYcBPM4G/7xBo6qDjq8lh4avpqNUw1oz2p1rfF5xh7 H3FD0Md1UfAM4Iw9uXCfOujO5Gkk1+hUD2jjlnGJd57HRKoUzlJ+ra1EivYKJTWa CUmCcEr2QXEU7dtKw1s9z5BGFTQaHZkRdRT4oUlgn3RJ9j0XLWyr2fOH6BKsEMxX 1O5YAwe5/Ph8L0TlF04m80G+l8Ca/ojfB7V2qwRqW7ClLhmT8IRAcaaC1uNZOTl3 a0HekNLhbKukInzgGzoMBlG3ilO68YT0JNX/npMSNvB0ZDS7b4mbNtHw8W2kQq1s kjrkkP2w2r0GXZW+lmnd6djeaRifwvM/fp+I9FU4QXkbxzXY50Iw6aw1pXBqVVbM Gqehdj8i+HffluoOsEdg26k08CfH1S1oDmQDoU1RNMClZODOQfqNtRxzpST4KwXk /WeWZszYo7abvE6pzuF5N8L2qiCmnK1U1z9nuGWqrsfd6ZuHJJ5tnRTC4XnE9NvJ u8OJHxFZWs+G1PLSaCZ7IszHh5Hn4mlEPT6x7OqH4zge46n6YJOBHcl1B/DRgHBb orynU4/oyXA+sav/Ekl4MiiHFTGgWkeCJ4DEKZnSdG8Tw8Bf01wn+4AuAkhCv5CE m5Ov2k+fNUeMWC2xHGHxj0z1hKZte7Tg/r96MSItu8PMKgBPwFQ= =hk5v -----END PGP SIGNATURE----- --3iqfx6deqp4ggs2f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170518213622.r66gzsjlvj76ujli>