On Fri, Jun 09, 2023 at 07:36:42AM -0400, Greg Wooledge wrote: > On Fri, Jun 09, 2023 at 06:20:07AM -0400, gene heskett wrote: > > On 6/9/23 00:46, tomas@tuxteam.de wrote: > > > This is actually the classical pattern of "layered configuration", which > > > is widespread in the UNIX world. You see that often with a system config > > > which can be overridden by a user config. > > > > > > Sometimes you have even three layers: distro (e.g. lib), local (etc) and > > > user. > > > > Thanks for the clarification Tomas. That would intimate the search order > > would be /home/$usr/someplace, /etc/someplace, /lib/someplace. Is that > > correct? > > Tomas is speaking in a general sense. There are many different programs > which use this TYPE of arrangement, or some subset of it. > > The exact search order would depend on which specific program is being > analzed. > > Also, sometimes it's not a case of "search through the following list > and use the first one you find". This would be the udev pattern: if there's something in /etc, use that, otherwise use the one in /lib. I.e. the /etc one REPLACES the /lib one. > Sometimes the list is traversed in > the other direction, and ALL configuration files are read, starting > with the generic distribution file, and then the local sysadmin's file, > and then the user's file, with the intent that the later files can > override the configuration elements established by the earlier files. This is typical for shell thingies: the $HOME ones AUGMENT/OVERRIDE the /etc ones. > Both ways are quite common. Thanks for all the gory details :-) Cheers -- t
Attachment:
signature.asc
Description: PGP signature