Re: Switching package to fragmented default configuration

2020-09-02 Thread John M. Harris Jr
On Wednesday, September 2, 2020 8:03:03 AM MST David Tardon wrote: > Hello, > > On Mon, 2020-08-31 at 23:46 -0700, John M. Harris Jr wrote: > > > On Monday, August 31, 2020 11:24:57 PM MST David Tardon wrote: > > > > > On Mon, 2020-08-31 at 00:08 -0700, John M. Harris Jr wrote: > > > > > > > >

Re: Switching package to fragmented default configuration

2020-09-02 Thread David Tardon
Hello, On Mon, 2020-08-31 at 23:46 -0700, John M. Harris Jr wrote: > On Monday, August 31, 2020 11:24:57 PM MST David Tardon wrote: > > On Mon, 2020-08-31 at 00:08 -0700, John M. Harris Jr wrote: > > > > > On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote: > > > > > > > https://blo

Re: Switching package to fragmented default configuration

2020-08-31 Thread John M. Harris Jr
On Monday, August 31, 2020 11:24:57 PM MST David Tardon wrote: > On Mon, 2020-08-31 at 00:08 -0700, John M. Harris Jr wrote: > > > On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote: > > > > > https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-a > > > nti-> hyster

Re: Switching package to fragmented default configuration

2020-08-31 Thread David Tardon
On Mon, 2020-08-31 at 00:08 -0700, John M. Harris Jr wrote: > On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote: > > https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-anti-> > > hysteresis/ > > touches on some of the benefits of "fragmented" configs. > > Perhaps

Re: Switching package to fragmented default configuration

2020-08-31 Thread John M. Harris Jr
On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote: > On Sat, Aug 29, 2020, at 2:19 PM, Igor Raits wrote: > > > > And only way to get to the distribution defaults is to download RPM > > with matching version, unpack it and get its /etc/foo.conf. > > > On ostree-based systems, the

Re: Switching package to fragmented default configuration

2020-08-29 Thread Colin Walters
On Sat, Aug 29, 2020, at 2:19 PM, Igor Raits wrote: > And only way to get to the distribution defaults is to download RPM > with matching version, unpack it and get its /etc/foo.conf. On ostree-based systems, the defaults for /etc are in /usr/etc, so you always have them - it needs this to do th

Re: Switching package to fragmented default configuration

2020-08-29 Thread Igor Raits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 2020-08-29 at 11:02 -0700, John M. Harris Jr wrote: > On Saturday, August 29, 2020 1:00:17 AM MST Samuel Sieb wrote: > > On 8/28/20 9:40 PM, John M. Harris Jr wrote: > > > > > Please don't invent a new logic, especially the one that systemd

Re: Switching package to fragmented default configuration

2020-08-29 Thread John M. Harris Jr
On Saturday, August 29, 2020 1:00:17 AM MST Samuel Sieb wrote: > On 8/28/20 9:40 PM, John M. Harris Jr wrote: > > > Please don't invent a new logic, especially the one that systemd does. > > This makes it very difficult to figure out where in the world the > > configuration file for a given progra

Re: Switching package to fragmented default configuration

2020-08-29 Thread Samuel Sieb
On 8/28/20 9:40 PM, John M. Harris Jr wrote: Please don't invent a new logic, especially the one that systemd does. This makes it very difficult to figure out where in the world the configuration file for a given program is. With systemd, sure, it's not so bad, as the System defaults go in /usr

Re: Switching package to fragmented default configuration

2020-08-28 Thread John M. Harris Jr
On Tuesday, August 4, 2020 9:32:35 AM MST Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Aug 04, 2020 at 05:11:49PM +0200, Miroslav Lichvar wrote: > > > I'm considering to split the default configuration file in the chrony > > package to make it easier for vendors, products, and configuration > > to

Re: Switching package to fragmented default configuration

2020-08-05 Thread Miroslav Lichvar
On Tue, Aug 04, 2020 at 06:26:37PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Aug 04, 2020 at 07:05:45PM +0200, Miroslav Lichvar wrote: > > That's possible (the paths could be hardcoded in the systemd unit > > file), but is it a good idea to force the users to use the new system? > > If so

Re: Switching package to fragmented default configuration

2020-08-04 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Aug 04, 2020 at 07:05:45PM +0200, Miroslav Lichvar wrote: > On Tue, Aug 04, 2020 at 04:32:35PM +, Zbigniew Jędrzejewski-Szmek wrote: > > It's nice to not require any files in /etc (so for example the admin > > can do 'rm -rf /etc/*' to restore vendor defaults). So instead of > > using /

Re: Switching package to fragmented default configuration

2020-08-04 Thread Neal Gompa
On Tue, Aug 4, 2020 at 1:28 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Aug 04, 2020 at 05:11:49PM +0200, Miroslav Lichvar wrote: > > I'm considering to split the default configuration file in the chrony > > package to make it easier for vendors, products, and configuration > > tools to over

Re: Switching package to fragmented default configuration

2020-08-04 Thread Chris Adams
Once upon a time, Miroslav Lichvar said: > The trouble is that a fragment having a different name cannot disable > servers specified in a different fragment. If anaconda wanted to > override the default servers, it would need to know the name of the > fragment. So, that brings up something I've b

Re: Switching package to fragmented default configuration

2020-08-04 Thread Miroslav Lichvar
On Tue, Aug 04, 2020 at 04:32:35PM +, Zbigniew Jędrzejewski-Szmek wrote: > It's nice to not require any files in /etc (so for example the admin > can do 'rm -rf /etc/*' to restore vendor defaults). So instead of > using /etc/chrony.conf to load other files, please consider just > building this

Re: Switching package to fragmented default configuration

2020-08-04 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Aug 04, 2020 at 05:11:49PM +0200, Miroslav Lichvar wrote: > I'm considering to split the default configuration file in the chrony > package to make it easier for vendors, products, and configuration > tools to override some specific settings (like the default NTP > servers) by dropping a fi

Switching package to fragmented default configuration

2020-08-04 Thread Miroslav Lichvar
I'm considering to split the default configuration file in the chrony package to make it easier for vendors, products, and configuration tools to override some specific settings (like the default NTP servers) by dropping a file into a directory, instead of having to modify a packaged config file. I