Date: Sun, 16 Feb 2020 08:54:16 -0500 From: Michael Watters <wattersm@watters.ws> To: freebsd-questions@freebsd.org Subject: Re: Technological advantages over Linux Message-ID: <34c12aae-1855-3837-209d-03bfc422a6bd@watters.ws> In-Reply-To: <20200215064911.GF1482@admin.sibptus.ru> References: <20200214121620.GA80657@admin.sibptus.ru> <BAF0D681-7C95-419E-A49C-993F0EA39748@kicp.uchicago.edu> <20200214195430.25365f87@moonstudio> <7371554e-82a3-a7aa-b764-ae2627e241d3@kicp.uchicago.edu> <20200214203134.17f6d4bd@moonstudio> <20200215064911.GF1482@admin.sibptus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/15/2020 1:49 AM, Victor Sudakov wrote: > Ralf Mardorf via freebsd-questions wrote: >> Another PITA on Linux machines are drop directories, overriding sane >> configs, providing everything in one place. >> >> IOW a user might rely on /etc/foo.conf , but an update despotic installs >> >> /etc/foo.d/10-bar.conf >> >> and >> >> /etc/foo.d/20-bra.conf >> >> overriding all the values chosen for bar and bra by the admin, stored >> in /etc/foo.conf . >> >> An update never ever would replace /etc/foo.conf . On Arch Linux it >> would be stored as /etc/foo.conf.pacnew , almost all Linux distros >> provide such a solution, but the admin is screwed, if an update does >> add a file to /etc/foo.d/ . > FreeBSD has taken this path too (looking at /etc/rc.conf.d/, /etc/cron.d > and numerous others). > > FreeBSD's config merging solutions (mergemaster for src updates and > freebsd-update calling sdiff) are pretty good IMHO. Drop directories are actually a good thing and make managing a system using configuration tools like puppet and ansible much easier. Want to add a cron job? Just drop a file in /usr/local/etc/cron.d. To disable the job just remove the file. You don't have to worry about conflicting with other job definitions or mess around with the user's crontab.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34c12aae-1855-3837-209d-03bfc422a6bd>